Description

When StrictMode is enabled, and FDT is run under React v19, we run into NPEs in the top-level FixedDataTableContainer component, causing the table to not function correctly.

In StrictMode runs the constructor and lifecycle methods of FixedDataTableContainer a second time.
The order I observed was as follows:

constructor
constructor
getDerivedStateFromProps
getDerivedStateFromProps
componentDidMount
componentWillUnmount
componentDidMount
getDerivedStateFromProps
getDerivedStateFromProps

So when running in StrictMode, the handlers/redux store gets initialized in the constructor, and then immediately gets destroyed in componentWillUnmount, leading the table to be in a destroyed state.

I'm fixing this by moving the initialization logic to both the constructor and componentDidMount, following what we did in #657 in the past.

Motivation and Context

Fixes #738.

How Has This Been Tested?

Tested with local examples running React v19.
Tested with a Vite client app running React v19.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.